E-mail with smart reply and roaming drafts

ABSTRACT

An electronic mail computing system has a smart reply system that that enables a smart reply feature that surfaces a user input mechanism that allows a user to reply to an e-mail message without downloading full content of the e-mail message to the user&#39;s client computing system. A draft roaming system interacts with the client computing system to allow a plurality of different user devices to access a draft electronic mail message, and interacts with the smart reply system so a draft can be generated using the smart reply feature.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is based on and claims the benefit of U.S.provisional patent application Ser. No. 62/415,915, filed Nov. 1, 2016,the content of which is hereby incorporated by reference in itsentirety, and is related to co-pending U.S. application Ser. No.15/349,493, filed Nov. 11, 2016 and U.S. application Ser. No.15/362,929, filed Nov. 29, 2016.

BACKGROUND

Computer systems are currently in wide use. Some such computer systemshost services that are accessed by client computing systems.

Hosted services can take a wide variety of different forms. Forinstance, some hosted services host a suite of applications, such as anelectronic mail application, a calendar application, task and contactapplications, etc. The hosted services can be accessed by clientcomponents of the hosted services that reside on a client machine. Forinstance, a client component may surface user interface functionalitythat allows a user to perform calendar functions (such as to scheduleappointments, etc.), email functions (such as to prepare and send e-mailmessages, receive e-mail messages, manage folders in an e-mail system,manage filters, etc.), add, delete and modify contact information, amonga wide variety of other things.

When the user performs these operations, the client component generatesdata that is synchronized to the remote server environment in which theservice is deployed. Similarly, the remote server environment may needto synchronize data from its environment to the client. By way ofexample, if the hosted service is an electronic mail service, and theuser has received new messages from other e-mail users, the service willsynchronize that information down to the client computing system, thenext time the user logs into the e-mail service.

Some hosted electronic mail services provide a draft roaming feature.This feature allows a user to begin drafting an e-mail message and,before the user is finished, save it as a draft. The user may then use adifferent device to log into the e-mail system at a later time. When theuser does this, the e-mail service provides the user with access to thedraft, even though the user is accessing the e-mail service through adifferent device than the one on which the draft was begun. Providingthis type of access (through different devices) to draft e-mail messagesthat a user began on a different device is referred to as a draftroaming feature.

Some e-mail messages are part of a very lengthy thread, which caninclude a large number of other messages. Similarly, some e-mailmessages have rather large attachments. A smart reply feature allows auser to reply to an e-mail message without loading the entire or fullcontent corresponding to the e-mail message, onto the user devicethrough which the user is accessing the service and generating thereply. By way of example, a user may receive an e-mail message that hasa large attachment. The user may wish to simply forward that message toa different user, along with the attachment. A smart reply featuremaintains the full e-mail message at the service (the body of the e-mailmessage and the associated attachment) and allows the user to generate aforwarding message, including a message body that has the text that theuser inputs. When the user sends that message, the service willautomatically attaches the attachment to the forwarding message, andsends it to the recipient. Thus, the user never needs to download theentire attachment in order to generate and send a reply. The same istrue of a lengthy e-mail thread. That is, using a smart reply feature,the user need not download the entire e-mail thread in order to reply toor forward a message in that thread. Instead, the service maintains thefull e-mail thread and receives the new content of the reply messagefrom the user, and then attaches the full e-mail thread before sendingit on to the recipient.

In addition, the synchronization mechanisms in such services often use aparticular protocol in order to synchronize content between the serviceand client devices. When a new synchronization mechanism is deployed, itoften uses a different protocol, which is incompatible with the protocolfrom the previous synchronization mechanism. As one example, when afirst synchronization mechanism is used to synchronize data between aservice and client systems, it may identify the objects that aresynchronized (e.g., the e-mail messages, calendar events, contacts,etc.) using a first type of object identifying mechanism. However, asecond synchronization mechanism may use a different type of objectidentifying mechanism in order to identify those objects. Therefore, ifa service is running with the first synchronization mechanism, butwishes to change or upgrade to the second synchronization mechanism,that process often requires the service to synchronize all of theapplication data with the second mechanism, even though much of it hasalready been synchronized with the first mechanism. This can take agreat deal of time, and cause disruption in the user experience.

Further, some services synchronize data between the service and a clientcomponent, upon a user logging into the service. For instance, when auser logs onto his or her e-mail service, the service may, at that time,begin synchronizing the user's inbox from the service to the clientdevice. The synchronization mechanism can be fairly complex. Forinstance, it may first need to identify the differences between theinbox representations on the client system and the service. This caninclude enumerating all objects in the inbox of both systems andcomparing them to identify items that need to be synchronized.Regardless of the particular synchronization mechanism that is used, itcan be relatively computationally expensive and it can be relativelytime consuming.

The discussion above is merely provided for general backgroundinformation and is not intended to be used as an aid in determining thescope of the claimed subject matter.

SUMMARY

An electronic mail computing system has a smart reply system that thatenables a smart reply feature that surfaces a user input mechanism thatallows a user to reply to an e-mail message without downloading fullcontent of the e-mail message to the user's client computing system. Adraft roaming system interacts with the client computing system to allowa plurality of different user devices to access a draft electronic mailmessage, and interacts with the smart reply system so a draft can begenerated using the smart reply feature.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter. The claimed subject matter is not limited to implementationsthat solve any or all disadvantages noted in the background.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B (collectively referred to herein as FIG. 1) show a blockdiagram of one example of a computing system architecture.

FIG. 2 is a block diagram showing one example of a secondsynchronization system in more detail.

FIGS. 3A and 3B (collectively referred to herein as FIG. 3) show a flowdiagram illustrating one example of the operation of the architectureshown in FIG. 1 in switching between first and second synchronizationsystems.

FIG. 4 is a block diagram showing one example of an on-line view systemin more detail.

FIG. 5 is a flow diagram illustrating one example of the operation ofthe system shown in FIG. 4 in surfacing an on-line view and asynchronized view.

FIGS. 6A and 6B (collectively referred to herein as FIG. 6) show a blockdiagram of one example of an electronic mail (email) systemarchitecture.

FIGS. 7A and 7B (collectively referred to herein as FIG. 7) show a flowdiagram illustrating one example of an operation of the email systemarchitecture shown in FIG. 6.

FIG. 8 is a block diagram showing one example of the architecturesillustrated in FIGS. 1 and 6, deployed in a cloud computingarchitecture.

FIGS. 9-11 show examples of mobile devices that can be used in thearchitectures shown in the previous Figures.

FIG. 12 is a block diagram showing one example of a computingenvironment that can be used in the architectures shown in the previousFigures.

DETAILED DESCRIPTION

FIGS. 1A and 1B (collectively referred to herein as FIG. 1) show a blockdiagram of one example of a computing system architecture 100.Architecture 100 includes service computing system 102 and clientcomputing system 104 that communicate with one another over network 106.Network 106 can be any of a wide variety of different types of networks,such as a wide area network, a local area network, etc.

In one example, service computing system 102 hosts a service that isaccessed by client computing system 104. Client computing system 104thus generates user interfaces 108 with user input mechanisms 110 forinteraction by user 112. User 112 illustratively interacts with userinput mechanisms 110 in order to control and manipulate client computingsystem 104 and ultimately service computing system 102. Beforedescribing the overall operation of architecture 100 in more detail, abrief description of some of the items in architecture 100, and theiroperation, will first be provided.

FIG. 1 shows that, in one example, service computing system 102 includesprocessors or servers 114, service functionality 116, on-line viewgeneration system 118, data store 120, view blending logic 122, (whichis shown in ghost on system 102 and on client computing system 104because it can reside either place) server side application 124, firstsynchronization system 126, second synchronization system 128, and itcan include other items 130. Data store 120, itself, can include firstapplication data 132, second application data 134, and it can includeother items 136. Server side application 124 can include functionalitylogic 138, application data location identifier 140, and it can alsoinclude other items.

Service functionality 116 illustratively includes logic andfunctionality that performs functions and operations to implement thehosted service or server side application 124. Therefore, functionality116 can manage virtual machines or hardware or other softwarecomponents. It can also perform a wide variety of other functions tohost server side application 124. On-line view generation system 118will be described in greater detail below with respect to FIGS. 4 and 5.Briefly, it illustratively generates an on-line, truncated view of datawhen a user logs onto the service. This can be displayed to the userwhile a synchronization system (such as first or second synchronizationsystem 126 or 128, respectively) begin synchronizing data between theservice and the client system. Once the synchronized data is ready, aview of the synchronized data can be used to replace the on-line view.

View blending logic 122 illustratively manages the operation of firstdisplaying the on-line view of the relevant data, and then displayingthe synchronized view, once it is ready. This can be done in a varietyof different ways, and this is also described in more detail below withrespect to FIGS. 4 and 5.

Server side application 124 illustratively includes functionality logic138 that implements the functionality of the server side application.For instance, where application 124 is an electronic mail (e-mail)application, then logic 138, in conjunction with service functionality116, can implement e-mail functionality that allows users to access thee-mail application and perform e-mail functions. Where application 124is a calendaring application, then functionality 138, in conjunctionwith functionality 116, allows the user to access the calendaringfunctions and perform different calendaring tasks. These are examplesonly and a wide variety of other services can be embodied in server sideapplication 124.

Application data location identifier 140 illustratively identifies, forapplication 124, where it is to access application data in data store120. For instance, service computing system 102 may be using a firstsynchronization system 126 that synchronizes data between clientcomputing system 104 and data store 120 in service computing system 102according to a first protocol. It may do that by synchronizing firstapplication data 132 which may be, for instance, user mailboxes,calendars, contact lists, tasks, notes, etc. In that case, applicationdata location identifier 140 will identify the location of firstapplication data 132 in data store 120. It will of course be understoodthat data store 120 can be local to computing system 102 or it can belocated elsewhere. In addition, it can be located at multiple differentlocations.

Regardless, it may be that service computing system 102 wishes to change(or upgrade) to synchronizing data with a second synchronization system128 that synchronizes data between client computing system 104 andservice computing system 102 according to a second protocol. Therefore,as is described in more detail below with respect to FIGS. 2 and 3,second synchronization system 128 may begin synchronizing data, assecond application data 134, even while first synchronization system 126is still performing synchronization operations to support server sideapplication 124. When second synchronization system 128 has synchronizedsufficient data, then it can change application data location identifier140 to point to second application data 134 so that server sideapplication 124 begins operating off second application data 134,instead of first application data 132. When second synchronizationsystem 128 has synchronized all of the first application data 132, thenthat data can be deleted and first synchronization system 126 can beremoved from service computing system 102 as well.

Client computing system 104, in the example shown in FIG. 1,illustratively includes one or more processors or servers 150, userpresence detector 152 (which can also be located on service computingsystem 102), client side application 154, data store 156, user interfacelogic 158, and it can include a wide variety of other clientfunctionality 160. User presence detector 152 can detect a number ofdifferent things on client computing system 104 to determine whetheruser 112 is present (at least whether the user is present with respectto the service side application 124 hosted by service computing system102). For instance, detector 152 can detect whether the user is loggedinto the service, whether the user has recently used the service,whether the user has used other items on client computing system 104,etc. It illustratively outputs a signal indicative of whether the user112 is present.

Client side application 154 can be a client component of server sideapplication 124. Therefore, it can use user interface logic 158 tosurface user interfaces 108 with user input mechanisms 110 that allowuser 112 to access both the client side application 154, and server sideapplication 124. In doing so, it can generate application data 162, andother data 164. For instance, user 112 can use client side application154 to generate an appointment on the user's calendar. This may bestored as application data 162. The synchronization system being used bycomputing system 102 then synchronizes that data to data tore 120 sothat it can be used by server side application 124 as well.

FIG. 2 is a block diagram showing one example of second synchronizationsystem 128, in more detail. In one example, it includes synchronizationstart logic 170, synchronization logic 172, handoff detection logic 174,and it can include a wide variety of other items 176. Synchronizationstart logic 170 illustratively detects when second synchronizationsystem 128 is to synchronize data between service computing system 102and client computing system 104. Synchronization logic 172illustratively performs the actual synchronization operations. It caninclude difference identifier logic 178, difference synchronizationlogic 180, and other items 182. Difference identifier logic 178identifies differences in the application data 162 and the applicationdata stored on data store 120. Difference synchronizer logic 180illustratively performs operations to synchronize that data betweenservice 102 and client computing system 104.

Handoff detection logic 174 can be used to detect when the handoffshould occur between first synchronization system 126 and secondsynchronization system 128, in a scenario where service computing system102 is in the process of switching from using first synchronizationsystem 126 to using second synchronization system 128. In one example,logic 174 includes synchronized data volume detector 184, comparisonlogic 186, handoff control signal generator logic 188 and it can includeother items 190.

Synchronized data volume detector 184 detects a volume of applicationdata that has been synchronized using second synchronization system 128.The volume can be an overall aggregate volume of data, or it can detectwhen certain key portions of data have been synchronized. For instance,when the server side application 124 is an e-mail application, it maydetect when the user's last week of e-mail messages have beensynchronized. When server side application 124 is a calendarapplication, logic 184 may detect when the current month on the user'scalendar, the previous month, and the next month, have all beensynchronized. Detector 184 may detect when other criteria are met aswell. Comparison logic 186 compares the detected volume (or detectedother criteria) and compares them to a threshold value which is to bemet before server side application 124 is handed off so that it operateson the second application data 184, instead of the first applicationdata 132. Handoff control signal generator logic 188 generates a controlsignal to adjust the application data location identifier 140 so that itnow identifies second application data 134 instead of first applicationdata 132. This is discussed in greater detail below with respect to FIG.3.

FIGS. 3A and 3B (collectively referred to herein as FIG. 3) show a flowdiagram illustrating one example of the operation of architecture 100,and second synchronization system 128, in synchronizing data andcontrolling server side application 124 to switch between using firstapplication data 132 that was synchronized using first synchronizationsystem 126, and second application data 134 that was synchronized usingsecond synchronization system 128. In doing so, it is first assumed thatthe service is running with first synchronization system 126synchronizing first application data 132, and that server sideapplication 124 is using first application data 132 to service requestsfrom the various client computing systems. It is also assumed that thesecond synchronization system 128 is deployed on the service computingsystem 102. This is indicated by block 200 in the flow diagram of FIG.3. Sync start logic 170 then detects the user presence as indicated byuser presence detector 152. This is indicated by block 202. This, asdescribed above, can be detected from a detector 152 on client computingsystem 104, as indicated by block 204, or from a detector on servicecomputing system 102, as indicated by block 206. It can be detected inother ways as well, and this is indicated by block 208.

In one example, second synchronization system 128 does not beginsynchronizing the application data according to the second protocolwhile the user is present. Therefore, if the user is not present, asindicated by block 210, then second synchronization system 128 beginssynchronizing second application data 134. This is indicated by block212.

In doing so, it does not yet switch over server side application 124 tobegin using second application data 134. This is indicated by block 214.As mentioned above, it synchronizes the data using a secondsynchronization protocol as indicated by block 216. It can synchronizethe data in other ways as well, and this is indicated by block 218.

At some point, synchronized data volume detector 184 detects a volume(or other characteristic) of the data synchronized. This is indicated byblock 220. Again, this can be an aggregate volume metric that identifiesthe aggregate volume of application data that has been synchronized bysecond synchronization system 128. This is indicated by block 222 in theflow diagram of FIG. 3. It can also detect whether key data records havebeen synchronized, as discussed above. This is indicated by block 224.It can detect the volume or other attributes of the data that have beensynchronized in other ways as well, and this is indicated by block 226.

Comparison logic 186 then determines whether the detected volume meetshandoff criteria for switching the application 124 from using firstapplication data 132 to using second application data 134. This isindicated by block 228 in the flow diagram of FIG. 3. If not, processingreturns to block 212 where second synchronization system 128 continuesto synchronize data. The handoff criteria can take a variety ofdifferent forms. For instance, it can be a threshold proportion of theapplication data as indicated by block 230. The criteria can be that allof the application data be synchronized as indicated by block 232. Itcan be a wide variety of other handoff criteria 234, as indicated byblock 234.

Once the detected data that has been synchronized by secondsynchronization system 128 meets the handoff criteria, then handoffcontrol signal generator logic 188 generates a control signal to switchthe server side application 124 to using data at the data location forthe second application data 134 synchronized using the secondsynchronization system. This is indicated by block 236 in the flowdiagram of FIG. 3. Second synchronization system 128 continues tosynchronize application data, as indicated by block 238.

Until all of the application data has been completely synchronized bysecond synchronization system 128, it may be that server sideapplication 124, even though it is using second application data 134,will receive a call for data that has not yet been synchronized bysecond synchronization system 128. This is indicated by blocks 240 and242 in the flow diagram of FIG. 3. When this occurs, then secondsynchronization system 128 directs server side application 124 toservice the call by accessing first application data 132. This isindicated by block 244 in the flow diagram of FIG. 3.

Once all of the application data has been synchronized by secondsynchronization system 128, then service computing system 102discontinues synchronizing data with first synchronization system 126.This is indicated by block 246 in flow diagram of FIG. 3. It thendeletes the first application data 132. This is indicated by block 248.

In doing this, it can be seen that second synchronization system 128begins synchronizing data, without the user ever knowing it. The serverside application is not switched over to using that synchronizationdata, until the service calls can most likely be serviced from the datasynchronized by second synchronization system 128. All the while, secondsynchronization system 128 continues to synchronize the applicationdata, until it is all synchronized, at which point the service can thenrun using only second synchronization system 128 to synchronize thedata. This allows switching to a different synchronization system toobtain all the benefits of such a system, even if it uses a differentsynchronization protocol, substantially invisible to the user.

FIG. 4 is a block diagram showing one example of on-line view generationsystem 118 in more detail. In one example, it includes a view calldetector 250, data accessing logic 252, truncation logic 254, viewgenerator logic 256, and it can include other items 258. View calldetector 250 detects when a call for a view of data has been made toserver side application 124. For instance, when application 124 is ane-mail system, the user 112 may log into the system and, at that point,a call to see the user's inbox may be generated by client computingsystem 104.

Data accessing logic 252 then accesses the relevant portion of theapplication data in data store 120 that is to be surfaced for the view.Truncation logic 254 truncates that data and view generator logic 256generates a view of the truncated data so that it can be immediatelyhanded to client computing system 104 for display to user 112. It willbe noted that on-line view generation system 118 does not wait for datato be synchronized between client computing system 104 and servicecomputing system 102, in order to generate the view. For instance, itmay simply take a view of the user's inbox from the data store 120 inservice computing system 102, before that data is synchronized with thedata in client computing system 104. In this way, at least the clientwill see the version of the inbox stored on service computing system102, very quickly. At the same time, the synchronization system will besynchronizing data in the client computing system 104 with data in theservice computing system 102 and when the synchronized data is ready, aview of the synchronized data can be generated and that view can replacethe on-line view that shows only the view of the data from the servicecomputing system data, before it is synchronized.

FIG. 5 is a flow diagram illustrating one example of this operation.View call detector 250 first detects a call to view application data.This is indicated by block 260 in the flow diagram of FIG. 5. This canoccur, as mentioned above, when the user logs into the service (such asthe user's e-mail system). This is indicated by block 262. It can bedetected in other way as well, and this is indicated by block 264.

At that point, the synchronization system on service computing system102 (for purposes of the present discussion, it will be assumed that itis second synchronization system 128) begins synchronizing theapplication data 162 on client computing system 104 with the secondapplication data 134 on service computing system 102. This is indicatedby block 266. Once the data has been synchronized, it generates asynchronized view showing the synchronized data. This is indicated byblock 268.

While system 128 is synchronizing the data, data accessing logic 252accesses the relevant application data 134. This is indicated by block270. Depending on the particular application 124, this may be data forthe user's inbox 272, for the user's calendar 274, or a wide variety ofother data 276.

Truncation logic 254 generates a truncated form of the relevant data.This is indicated by block 278. Again, the truncated view will be ofonly non-synchronized data (e.g., server side only data that has notbeen synchronized service the current call was made to view the data).This is indicated by block 280. The truncated view can include a datalimit (such as the top N message threads in the user's inbox). This isindicated by block 282. It can include individual data recordtruncation, (such as truncating a message thread to only the messageheaders). This is indicated by block 284. The truncation can take a widevariety of other forms as well, and this is indicated by block 286.

View generator logic 156 then generates an on-line view with thetruncated data. This is indicated by block 288. For example, the viewmay be a view of the user's inbox showing only the message threadheaders, instead of additional message content. It will be noted thatthe views can be generated on the client system or on the service.

System 118 then uses view blending logic 122 to surface the on-lineview, through client side application 154, for user 112. Again, it willbe noted that logic 122, and thus the view blending, can take placeeither on system 102 or on system 104. This is indicated by block 290 inthe flow diagram of FIG. 5.

Once the synchronized view is generated, however, view blending logic122 surfaces the synchronized view. This is indicated by block 292. Forinstance, as data items in the user's inbox are synchronized, thatportion of the on-line view can be replaced by a view of thesynchronized data. This is indicated by block 294. In another example,the entire inbox is synchronized before the synchronized view replacesthe on-line view. This is indicated by block 296. Surfacing thesynchronized view can be done in other ways as well, and this isindicated by block 298.

It can thus be seen that, using this approach, a user very quicklyreceives the server side view of the user's data (e.g., the user'sinbox) as soon as the user logs into the system. That view is notdelayed while synchronization takes place. Instead, the view isgenerated of only the server side data, and when the data is actuallysynchronized, then a view of the synchronized data is generated and itreplaces the on-line view.

FIGS. 6A and 6B (collectively referred to herein as FIG. 6) show a blockdiagram showing another example of a computing system architecture 300,in which service computing system 102 is an electronic mail computingsystem 102. It illustratively hosts an electronic mail service for aplurality of different client systems 304-306. Each of the clientsystems 304-306 can generate user interfaces 308-310, with user inputmechanisms 312-314 for interaction by users 316-318, respectively. Theusers can interact with the user input mechanisms in order to controlthe corresponding client systems and e-mail computing system 102. Beforethe operation of architecture 300 is described in more detail, a briefdescription of some of the items in architecture 300, and theiroperation, will first be described.

E-mail computing system 302 can include one or more processors orservers 320, e-mail functionality logic 322, a synchronization system324 (which can be either first or second synchronization system 126 or128 from FIG. 1, or a different one), smart reply system 326, draftroaming system 328, data store 330, and it can include a wide variety ofother items 332.

E-mail functionality logic 322 illustratively performs functions andoperations to implement the operation of e-mail computing system 302.For instance, it illustratively performs operations that allow users todraft, reply to, delete or modify e-mail messages, perform folderoperations, filter operations, send and receive e-mail messages, among awide variety of other functions.

Synchronization system 324 illustratively synchronizes the e-mail databetween e-mail computing system 302 and the various client systems304-306.

Smart reply system 326 can include smart reply detection logic 334,message truncation logic 336, full message generation logic 338, draftchange detector logic 340, and it can include other items 342. Smartreply detection logic 334 detects when a user wishes to use the smartreply feature so that a user can reply to (or forward) an e-mail messagewithout downloading the entire content of the e-mail message onto theuser's device. Message truncation logic 336 then truncates the messagethat the user is replying to and downloads only that portion onto theclient system. Full message generation logic 338 illustrativelygenerates and maintains a full message so that when the user sends thereply, the full message can be sent to the desired recipient, and notjust the truncated portion that the user downloaded. Draft changedetector logic 340 detects when a draft that the user has previouslyworked on has changed, so that the smart reply features should not beused or so that the full message should be downloaded to the clientsystem.

Draft roaming system 328 can include draft detection logic 344, draftmaintenance logic 346, and it can include other items 348. Draftdetection logic 344 detects when a user begins to draft an e-mailmessage (such as a reply). Draft maintenance logic 346 illustrativelymaintains that draft in data store 330 so that the user can have accessto it, even if the user logs onto the e-mail computing system 302 usinga different device. This is referred to as roaming the draft acrossdifferent devices.

Data store 330 can include one or more message threads 350-352, one ormore draft messages 354-356, and it can include a wide variety of otheritems 358. Each message thread 350 can include header data 360 thatdefines one or more headers in the message thread. It can also includeone or more messages 362 in the thread, as well as any attachments 364that belong to the thread.

Draft messages 354-356 can include a unique body portion 366 and 368,respectively, as well as an old mail thread portion 370-372. By way ofexample, assume that draft 354 is a draft that has been started by user316 and is in reply to an old message thread. Unique body portion 366 ofthe draft will be that portion that the user 316 is authoring in thereply message. The old mail thread 370 will illustratively correspond tothe information in a message thread 350 or 352, for example, thatcontains all of the prior information in that thread, to which the useris replying.

Each client system 304-306 can include one or more processors or servers380, a client component 382, a data store 384, user interface logic 386,and it can include a wide variety of other items 388. Client component382 may be a client component of the electronic mail system being hostedby electronic mail computing system 302. Data store 384 can storeinformation generated or maintained by client component 382. Userinterface logic 386, either by itself or under the control of anotheritem, can illustratively generate user interfaces 308 and user inputmechanisms 312, and detect user interaction with them.

In overall operation, smart reply system 326 detects when a user beginstyping a reply message and determines whether the user has selected touse the smart reply feature. When the reply is a draft (in that the userlogs out of the computing system or navigates away from the reply beforesending the reply), draft detection logic 344 detects that the reply isa draft and that the user has invoked the smart reply feature. Draftmaintenance logic 346 illustratively stores the draft (such as draft354) in data store 330 and maintains it in a way so that it isaccessible by user 316 using any of a variety of other devices. In doingso, logic 346 accesses full message generation logic 338 to store thedraft as a full message which includes the unique body portion 366 andthe old mail thread portion 370. When the user again accesses draft 354,the unique body portion 366 can be downloaded to the client system 304by message truncation logic 336 in smart reply system 326 so that theuser still need not download the full draft message (including the oldmail thread 370). Then, when the user finishes the draft and hits a sendactuator, full message generation logic 338 again attaches the fullmessage content (e.g., the old message thread 370) to the draft andsends it to the desired recipient.

Draft change detector logic 340 can detect whether the draft has changedsince it was created by the user. For instance, it may be that, in themessage thread, another user has include in-line comments in the oldmail thread 370. In that case, when user 316 again accesses the draft354, the full message will be downloaded to the user so that he or shecan see that the old message thread has now been modified with theinsertion of in-line comments.

FIGS. 7A and 7B (collectively referred to herein as FIG. 7) show oneexample of the operation of architecture 300, shown in FIG. 6, inimplementing both the smart reply feature and the draft roaming featureon the same e-mail service.

Draft detection logic 344 first detects creation of a draft response bya user of a client system 304. This is indicated by block 400 in theflow diagram of FIG. 7.

Smart reply detection logic 334 then detects that the user has invokedthe smart reply feature. This is indicated by block 402. This can bedone, for instance, by surfacing a user input mechanism that allows theuser to choose the smart reply feature. It can be done in other ways aswell.

When the user has created the draft, full message generation logic 338generates a full message of the draft (both containing the unique bodyportion 366 and the old mail thread 370 and any attachments), and savesit in data store 330. This is indicated by block 404.

Draft maintenance logic 346 then roams the unique portion of the draftto other devices. This is indicated by block 406. For instance, if user316 accesses e-mail computing system 302 using a different device, theuser will have access to the unique body portion 366 in the smart replymode as well. This is indicated by block 408.

Draft change detector logic 340 then detects whether the old mail threadhas changed since the user created the draft. This is indicated by block410. If not, then message truncation logic 336 identifies the uniquebody portion 366 and synchronizes that to client system 304 so the usercan continue to work on the draft. This is indicated by blocks 412 and414 in the flow diagram of FIG. 7.

However, if, at block 412, it is determined that the old mail thread haschanged since the user created the draft, then full message generationlogic 338 accesses the full content of the draft 354 and syncs the fulldraft to the new device through which the user is currently accessinge-mail computing system 302. This is indicated by blocks 416 and 418 inthe flow diagram of FIG. 7.

In either case (whether the user is still accessing the draft using thesmart reply feature, or whether the user is accessing the full draft),e-mail computing system 302 detects when the user actuates the sendactuator to send the draft to the desired recipients. This is indicatedby block 420 in the flow diagram of FIG. 7.

Smart reply detection logic 334 determines whether the draft is stillbeing accessed in the smart reply mode as indicated by block 422. Ifnot, then the user is already accessing the full draft and that draft issimply sent to the recipient as indicated by block 424.

However, if, at block 422, it is determined that the user is stillaccessing the draft in the smart reply mode, then full messagegeneration logic 338 again forms the full content of the reply messageby adding the old mail threads 370 to the unique body portion 366 (alongwith any attachments). Stitching together the full draft in this way isindicated by block 426 in FIG. 7. Again, the full draft is then sent asindicated by block 424.

It can thus be seen that the present description enables a single e-mailsystem to include not only a smart reply system 326 that implements asmart reply feature, but also to include a draft roaming system 328 thatimplements the draft roaming feature. This improves the computing systemitself, as well as the user experience.

It will be noted that the above discussion has described a variety ofdifferent systems, components and/or logic. It will be appreciated thatsuch systems, components and/or logic can be comprised of hardware items(such as processors and associated memory, or other processingcomponents, some of which are described below) that perform thefunctions associated with those systems, components and/or logic. Inaddition, the systems, components and/or logic can be comprised ofsoftware that is loaded into a memory and is subsequently executed by aprocessor or server, or other computing component, as described below.The systems, components and/or logic can also be comprised of differentcombinations of hardware, software, firmware, etc., some examples ofwhich are described below. These are only some examples of differentstructures that can be used to form the systems, components and/or logicdescribed above. Other structures can be used as well.

The present discussion has mentioned processors and servers. In oneembodiment, the processors and servers include computer processors withassociated memory and timing circuitry, not separately shown. They arefunctional parts of the systems or devices to which they belong and areactivated by, and facilitate the functionality of the other componentsor items in those systems.

Also, a number of user interface displays have been discussed. They cantake a wide variety of different forms and can have a wide variety ofdifferent user actuatable input mechanisms disposed thereon. Forinstance, the user actuatable input mechanisms can be text boxes, checkboxes, icons, links, drop-down menus, search boxes, etc. They can alsobe actuated in a wide variety of different ways. For instance, they canbe actuated using a point and click device (such as a track ball ormouse). They can be actuated using hardware buttons, switches, ajoystick or keyboard, thumb switches or thumb pads, etc. They can alsobe actuated using a virtual keyboard or other virtual actuators. Inaddition, where the screen on which they are displayed is a touchsensitive screen, they can be actuated using touch gestures. Also, wherethe device that displays them has speech recognition components, theycan be actuated using speech commands.

A number of data stores have also been discussed. It will be noted theycan each be broken into multiple data stores. All can be local to thesystems accessing them, all can be remote, or some can be local whileothers are remote. All of these configurations are contemplated herein.

Also, the figures show a number of blocks with functionality ascribed toeach block. It will be noted that fewer blocks can be used so thefunctionality is performed by fewer components. Also, more blocks can beused with the functionality distributed among more components.

FIG. 9 is a block diagram of architecture 100, shown in FIG. 1, andarchitecture 300 shown in FIG. 6 except that the elements are disposedin a cloud computing architecture 500. Cloud computing providescomputation, software, data access, and storage services that do notrequire end-user knowledge of the physical location or configuration ofthe system that delivers the services. In various embodiments, cloudcomputing delivers the services over a wide area network, such as theinternet, using appropriate protocols. For instance, cloud computingproviders deliver applications over a wide area network and they can beaccessed through a web browser or any other computing component.Software or components of architectures 100 and/or 300 as well as thecorresponding data, can be stored on servers at a remote location. Thecomputing resources in a cloud computing environment can be consolidatedat a remote data center location or they can be dispersed. Cloudcomputing infrastructures can deliver services through shared datacenters, even though they appear as a single point of access for theuser. Thus, the components and functions described herein can beprovided from a service provider at a remote location using a cloudcomputing architecture. Alternatively, they can be provided from aconventional server, or they can be installed on client devicesdirectly, or in other ways.

The description is intended to include both public cloud computing andprivate cloud computing. Cloud computing (both public and private)provides substantially seamless pooling of resources, as well as areduced need to manage and configure underlying hardware infrastructure.

A public cloud is managed by a vendor and typically supports multipleconsumers using the same infrastructure. Also, a public cloud, asopposed to a private cloud, can free up the end users from managing thehardware. A private cloud may be managed by the organization itself andthe infrastructure is typically not shared with other organizations. Theorganization still maintains the hardware to some extent, such asinstallations and repairs, etc.

In the example shown in FIG. 8, some items are similar to those shown inFIGS. 1 and 6 and they are similarly numbered. FIG. 8 specifically showsthat service computing system 100 and/or email computing system 302 canbe located in cloud 502 (which can be public, private, or a combinationwhere portions are public while others are private). Therefore, theusers can use user devices 504 to access those systems through cloud502.

FIG. 8 also depicts another example of a cloud architecture. FIG. 8shows that it is also contemplated that some elements of architectures100 and 300 can be disposed in cloud 502 while others are not. By way ofexample, data stores 120, 330 can be disposed outside of cloud 502, andaccessed through cloud 502. In another example, synchronization system126, 128 or other items can be outside of cloud 502. Regardless of wherethey are located, they can be accessed directly by devices 504, througha network (either a wide area network or a local area network), they canbe hosted at a remote site by a service, or they can be provided as aservice through a cloud or accessed by a connection service that residesin the cloud. All of these architectures are contemplated herein.

It will also be noted that architectures 100 and/or 300, or portions ofthem, can be disposed on a wide variety of different devices. Some ofthose devices include servers, desktop computers, laptop computers,tablet computers, or other mobile devices, such as palm top computers,cell phones, smart phones, multimedia players, personal digitalassistants, etc.

FIG. 9 is a simplified block diagram of one illustrative embodiment of ahandheld or mobile computing device that can be used as a user's orclient's hand held device 16, in which the present system (or parts ofit) can be deployed. FIGS. 10-11 are examples of handheld or mobiledevices.

FIG. 9 provides a general block diagram of the components of a clientdevice 16 that can run components of architecture 100, 300 or thatinteracts with architectures 100, 300, or both. In the device 16, acommunications link 13 is provided that allows the handheld device tocommunicate with other computing devices and under some embodimentsprovides a channel for receiving information automatically, such as byscanning Examples of communications link 13 include an infrared port, aserial/USB port, a cable network port such as an Ethernet port, and awireless network port allowing communication though one or morecommunication protocols including General Packet Radio Service (GPRS),LTE, HSPA, HSPA+ and other 3G and 4G radio protocols, 1Xrtt, and ShortMessage Service, which are wireless services used to provide cellularaccess to a network, as well as Wi-Fi protocols, and Bluetooth protocol,which provide local wireless connections to networks.

In other examples, applications or systems are received on a removableSecure Digital (SD) card that is connected to a SD card interface 15. SDcard interface 15 and communication links 13 communicate with aprocessor 17 (which can also embody processors or servers from previousFigures) along a bus 19 that is also connected to memory 21 andinput/output (I/O) components 23, as well as clock 25 and locationsystem 27.

I/O components 23, in one embodiment, are provided to facilitate inputand output operations. I/O components 23 for various embodiments of thedevice 16 can include input components such as buttons, touch sensors,multi-touch sensors, optical or video sensors, voice sensors, touchscreens, proximity sensors, microphones, tilt sensors, and gravityswitches and output components such as a display device, a speaker, andor a printer port. Other I/O components 23 can be used as well.

Clock 25 illustratively comprises a real time clock component thatoutputs a time and date. It can also, illustratively, provide timingfunctions for processor 17.

Location system 27 illustratively includes a component that outputs acurrent geographical location of device 16. This can include, forinstance, a global positioning system (GPS) receiver, a LORAN system, adead reckoning system, a cellular triangulation system, or otherpositioning system. It can also include, for example, mapping softwareor navigation software that generates desired maps, navigation routesand other geographic functions.

Memory 21 stores operating system 29, network settings 31, applications33, application configuration settings 35, data store 37, communicationdrivers 39, and communication configuration settings 41. Memory 21 caninclude all types of tangible volatile and non-volatilecomputer-readable memory devices. It can also include computer storagemedia (described below). Memory 21 stores computer readable instructionsthat, when executed by processor 17, cause the processor to performcomputer-implemented steps or functions according to the instructions.Similarly, device 16 can have a client system 24 which can run variousbusiness applications or embody parts or all of client systems 104, 304,306. Processor 17 can be activated by other components to facilitatetheir functionality as well.

Examples of the network settings 31 include things such as proxyinformation, Internet connection information, and mappings. Applicationconfiguration settings 35 include settings that tailor the applicationfor a specific enterprise or user. Communication configuration settings41 provide parameters for communicating with other computers and includeitems such as GPRS parameters, SMS parameters, connection user names andpasswords.

Applications 33 can be applications that have previously been stored onthe device 16 or applications that are installed during use, althoughthese can be part of operating system 29, or hosted external to device16, as well.

FIG. 10 shows one embodiment in which device 16 is a tablet computer600. In FIG. 10, computer 600 is shown with user interface displayscreen 602. Screen 602 can be a touch screen (so touch gestures from auser's finger can be used to interact with the application) or apen-enabled interface that receives inputs from a pen or stylus. It canalso use an on-screen virtual keyboard. Of course, it might also beattached to a keyboard or other user input device through a suitableattachment mechanism, such as a wireless link or USB port, for instance.Computer 600 can also illustratively receive voice inputs as well.

FIG. 11 shows that the device can be a smart phone 71. Smart phone 71has a touch sensitive display 73 that displays icons or tiles or otheruser input mechanisms 75. Mechanisms 75 can be used by a user to runapplications, make calls, perform data transfer operations, etc. Ingeneral, smart phone 71 is built on a mobile operating system and offersmore advanced computing capability and connectivity than a featurephone.

Note that other forms of the devices 16 are possible.

FIG. 12 is one example of a computing environment in which architecture100 and/or 300, or parts of them, (for example) can be deployed. Withreference to FIG. 12, an example system for implementing someembodiments includes a general-purpose computing device in the form of acomputer 810. Components of computer 810 may include, but are notlimited to, a processing unit 820 (which can comprise processors orservers from previous Figures), a system memory 830, and a system bus821 that couples various system components including the system memoryto the processing unit 820. The system bus 821 may be any of severaltypes of bus structures including a memory bus or memory controller, aperipheral bus, and a local bus using any of a variety of busarchitectures. By way of example, and not limitation, such architecturesinclude Industry Standard Architecture (ISA) bus, Micro ChannelArchitecture (MCA) bus, Enhanced ISA (EISA) bus, Video ElectronicsStandards Association (VESA) local bus, and Peripheral ComponentInterconnect (PCI) bus also known as Mezzanine bus. Memory and programsdescribed with respect to FIGS. 1 and/or 6 can be deployed incorresponding portions of FIG. 12.

Computer 810 typically includes a variety of computer readable media.Computer readable media can be any available media that can be accessedby computer 810 and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer readable media may comprise computer storage mediaand communication media. Computer storage media is different from, anddoes not include, a modulated data signal or carrier wave. It includeshardware storage media including both volatile and nonvolatile,removable and non-removable media implemented in any method ortechnology for storage of information such as computer readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by computer 810. Communication media typically embodiescomputer readable instructions, data structures, program modules orother data in a transport mechanism and includes any informationdelivery media. The term “modulated data signal” means a signal that hasone or more of its characteristics set or changed in such a manner as toencode information in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared and other wireless media. Combinations of any of the aboveshould also be included within the scope of computer readable media.

The system memory 830 includes computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) 831and random access memory (RAM) 832. A basic input/output system 833(BIOS), containing the basic routines that help to transfer informationbetween elements within computer 810, such as during start-up, istypically stored in ROM 831. RAM 832 typically contains data and/orprogram modules that are immediately accessible to and/or presentlybeing operated on by processing unit 820. By way of example, and notlimitation, FIG. 12 illustrates operating system 834, applicationprograms 835, other program modules 836, and program data 837.

The computer 810 may also include other removable/non-removablevolatile/nonvolatile computer storage media. By way of example only,FIG. 12 illustrates a hard disk drive 841 that reads from or writes tonon-removable, nonvolatile magnetic media, and an optical disk drive 855that reads from or writes to a removable, nonvolatile optical disk 856such as a CD ROM or other optical media. Other removable/non-removable,volatile/nonvolatile computer storage media that can be used in theexemplary operating environment include, but are not limited to,magnetic tape cassettes, flash memory cards, digital versatile disks,digital video tape, solid state RAM, solid state ROM, and the like. Thehard disk drive 841 is typically connected to the system bus 821 througha non-removable memory interface such as interface 840, and optical diskdrive 855 are typically connected to the system bus 821 by a removablememory interface, such as interface 850.

Alternatively, or in addition, the functionality described herein can beperformed, at least in part, by one or more hardware logic components.For example, and without limitation, illustrative types of hardwarelogic components that can be used include Field-programmable Gate Arrays(FPGAs), Program-specific Integrated Circuits (ASICs), Program-specificStandard Products (ASSPs), System-on-a-chip systems (SOCs), ComplexProgrammable Logic Devices (CPLDs), etc.

The drives and their associated computer storage media discussed aboveand illustrated in FIG. 12, provide storage of computer readableinstructions, data structures, program modules and other data for thecomputer 810. In FIG. 12, for example, hard disk drive 841 isillustrated as storing operating system 844, application programs 845,other program modules 846, and program data 847. Note that thesecomponents can either be the same as or different from operating system834, application programs 835, other program modules 836, and programdata 837. Operating system 844, application programs 845, other programmodules 846, and program data 847 are given different numbers here toillustrate that, at a minimum, they are different copies.

A user may enter commands and information into the computer 810 throughinput devices such as a keyboard 862, a microphone 863, and a pointingdevice 861, such as a mouse, trackball or touch pad. Other input devices(not shown) may include a joystick, game pad, satellite dish, scanner,or the like. These and other input devices are often connected to theprocessing unit 820 through a user input interface 860 that is coupledto the system bus, but may be connected by other interface and busstructures, such as a parallel port, game port or a universal serial bus(USB). A visual display 891 or other type of display device is alsoconnected to the system bus 821 via an interface, such as a videointerface 890. In addition to the monitor, computers may also includeother peripheral output devices such as speakers 897 and printer 896,which may be connected through an output peripheral interface 895.

The computer 810 is operated in a networked environment using logicalconnections to one or more remote computers, such as a remote computer880. The remote computer 880 may be a personal computer, a hand-helddevice, a server, a router, a network PC, a peer device or other commonnetwork node, and typically includes many or all of the elementsdescribed above relative to the computer 810. The logical connectionsdepicted in FIG. 12 include a local area network (LAN) 871 and a widearea network (WAN) 873, but may also include other networks. Suchnetworking environments are commonplace in offices, enterprise-widecomputer networks, intranets and the Internet.

When used in a LAN networking environment, the computer 810 is connectedto the LAN 871 through a network interface or adapter 870. When used ina WAN networking environment, the computer 810 typically includes amodem 872 or other means for establishing communications over the WAN873, such as the Internet. The modem 872, which may be internal orexternal, may be connected to the system bus 821 via the user inputinterface 860, or other appropriate mechanism. In a networkedenvironment, program modules depicted relative to the computer 810, orportions thereof, may be stored in the remote memory storage device. Byway of example, and not limitation, FIG. 12 illustrates remoteapplication programs 885 as residing on remote computer 880. It will beappreciated that the network connections shown are exemplary and othermeans of establishing a communications link between the computers may beused.

It should also be noted that the different embodiments described hereincan be combined in different ways. That is, parts of one or moreembodiments can be combined with parts of one or more other embodiments.All of this is contemplated herein.

Example 1 is a computing system, comprising:

electronic mail (email) functionality on an email service thatdetermines that a user is generating, on a first client device, a draftresponse to an email message in a mailbox for the user, the emailmessage including a full content portion;

a smart reply system that truncates the email message, to obtain atruncated email message that is less than the full content portion ofthe email message, and sends the truncated email message to the firstclient device for generation of the draft response; and

a draft roaming system that saves the draft response on the emailservice for access by the user from a second client device, the smartreply system sending the truncated message and a unique portion of thedraft response, entered in the draft response, to the second clientdevice in response to detection of the user accessing the draft responsefrom the second client device.

Example 2 is the computing system of any or all previous exampleswherein the smart reply system comprises:

full message generation logic configured to detect actuation of a sendactuator to send the draft response and to generate a full messageincluding the unique portion of the draft response and the full contentportion of the email message, the email functionality sending the fullmessage.

Example 3 is the computing system of any or all previous exampleswherein the smart reply system comprises:

message truncation logic configured to generate the truncated message;and

smart reply detection logic configured to detect a smart reply inputfrom the first client device and, in response, control the messagetruncation logic to generate the truncated message.

Example 4 is the computing system of any or all previous exampleswherein the smart reply system comprises:

draft change detector logic configured to detect a change in the fullcontent portion of the draft response and control the draft roamingsystem to send the full content portion of the draft response, alongwith the unique portion, to the second client device in response todetection of the user accessing the draft response from the secondclient device.

Example 5 is the computing system of any or all previous exampleswherein the draft roaming system comprises:

draft maintenance logic configured to save the draft response on theemail service as a draft in the mailbox for the user with a smart replyindicator indicating that the smart reply input, corresponding to thedraft response, was detected by the smart reply detection logic.

Example 6 is the computing system of any or all previous examples andfurther comprising:

a data store storing the draft response, accessible by the first andsecond client devices.

Example 7 is the computing system of any or all previous exampleswherein the full content portion of the email message comprises a mailthread portion indicative of a full message thread corresponding to theemail message, and an attachment, and wherein the full messagegeneration logic is configured to detect actuation of the send actuatorto send the draft response and to generate the full message includingthe unique portion of the draft response, the mail thread portion andthe attachment.

Example 8 is a computer implemented method, comprising:

detecting, on an email server, that a user is generating, on a firstclient device, a draft response to an email message in a mailbox for theuser, the email message including a full content portion;

truncating the email message, to obtain a truncated email message thatis less than the full content portion of the email message, on the emailserver;

sending the truncated email message to the first client device forgeneration of the draft response;

saving the draft response on the email server for access by the userfrom a second client device;

detecting, on the email server, the user accessing the draft responsefrom the second client device; and

sending the truncated message and a unique portion of the draftresponse, entered in the draft response, to the second client device inresponse to detecting the user accessing the draft response from thesecond client device.

Example 9 is the computer implemented method of any or all previousexamples and further comprising:

detecting, at the email server, actuation of a send actuator, on thesecond client device, to send the draft response;

generating, at the email server, a full message including the uniqueportion of the draft response and the full content portion of the emailmessage; and

sending the full message to a recipient.

Example 10 is the computer implemented method of any or all previousexamples and further comprising:

detecting a smart reply input from the first client device; and

in response, generating the truncated message.

Example 11 is the computer implemented method of any or all previousexamples and further comprising:

detecting the user accessing the draft response from the second clientdevice;

detecting a change in the full content portion of the draft response;and

sending the full content portion of the draft response, along with theunique portion, to the second client device.

Example 12 is the computer implemented method of any or all previousexamples wherein saving the draft response on the email servercomprises:

saving the draft response on the email service as a draft in the mailboxfor the user with a smart reply indicator indicating that the smartreply input, corresponding to the draft response, was detected.

Example 13 is the computer implemented method of any or all previousexamples and further comprising:

storing the draft response in a cloud-based data store, accessible bythe first and second client devices through the email server.

Example 14 is the computer implemented method of any or all previousexamples wherein the full content portion of the email message comprisesa mail thread portion indicative of a full message thread correspondingto the email message, and an attachment, and wherein generating the fullmessage comprises:

detecting actuation of the send actuator to send the draft response; and

generating the full message including the unique portion of the draftresponse, the mail thread portion and the attachment.

Example 15 is a computing system, comprising:

electronic mail (email) functionality on a hosted email service thatdetermines that a user is generating, on a first client device, a draftresponse to an email message in a mailbox for the user, the emailmessage including a full content portion;

a smart reply system that truncates the email message, to obtain atruncated email message that is less than the full content portion ofthe email message, and sends the truncated email message to the firstclient device for generation of the draft response;

a draft roaming system that saves the draft response on the hosted emailservice for access by the user from a second client device, the smartreply system sending the truncated message and a unique portion of thedraft response, entered in the draft response, to the second clientdevice in response to detection of the user accessing the draft responsefrom the second client device; and

full message generation logic configured to detect actuation of a sendactuator to send the draft response and to generate a full messageincluding the unique portion of the draft response and the full contentportion of the email message, the email functionality sending the fullmessage.

Example 16 is the computing system of any or all previous exampleswherein the smart reply system comprises:

message truncation logic configured to generate the truncated message;and

smart reply detection logic configured to detect a smart reply inputfrom the first client device and, in response, control the messagetruncation logic to generate the truncated message.

Example 17 is the computing system of any or all previous exampleswherein the smart reply system comprises:

draft change detector logic configured to detect a change in the fullcontent portion of the draft response and control the draft roamingsystem to send the full content portion of the draft response, alongwith the unique portion, to the second client device in response todetection of the user accessing the draft response from the secondclient device.

Example 18 is the computing system of any or all previous exampleswherein the draft roaming system comprises:

draft maintenance logic configured to save the draft response on hostedthe email service as a draft in the mailbox for the user with a smartreply indicator indicating that the smart reply input, corresponding tothe draft response, was detected by the smart reply detection logic.

Example 19 is the computing system of any or all previous examples andfurther comprising:

a cloud-based data store storing the draft response, accessible by thefirst and second client devices through the hosted email service.

Example 20 is the computing system of any or all previous exampleswherein the full content portion of the email message comprises a mailthread portion indicative of a full message thread corresponding to theemail message, and an attachment, and wherein the full messagegeneration logic is configured to detect actuation of the send actuatorto send the draft response and to generate the full message includingthe unique portion of the draft response, the mail thread portion andthe attachment.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

What is claimed is:
 1. A computing system, comprising: electronic mail (email) functionality on an email service that determines that a user is generating, on a first client device, a draft response to an email message in a mailbox for the user, the email message including a full content portion; a smart reply system that truncates the email message, to obtain a truncated email message that is less than the full content portion of the email message, and sends the truncated email message to the first client device for generation of the draft response; and a draft roaming system that saves the draft response on the email service for access by the user from a second client device, the smart reply system sending the truncated message and a unique portion of the draft response, entered in the draft response, to the second client device in response to detection of the user accessing the draft response from the second client device.
 2. The computing system of claim 1 wherein the smart reply system comprises: full message generation logic configured to detect actuation of a send actuator to send the draft response and to generate a full message including the unique portion of the draft response and the full content portion of the email message, the email functionality sending the full message.
 3. The computing system of claim 2 wherein the smart reply system comprises: message truncation logic configured to generate the truncated message; and smart reply detection logic configured to detect a smart reply input from the first client device and, in response, control the message truncation logic to generate the truncated message.
 4. The computing system of claim 3 wherein the smart reply system comprises: draft change detector logic configured to detect a change in the full content portion of the draft response and control the draft roaming system to send the full content portion of the draft response, along with the unique portion, to the second client device in response to detection of the user accessing the draft response from the second client device.
 5. The computing system of claim 3 wherein the draft roaming system comprises: draft maintenance logic configured to save the draft response on the email service as a draft in the mailbox for the user with a smart reply indicator indicating that the smart reply input, corresponding to the draft response, was detected by the smart reply detection logic.
 6. The computing system of claim 5 and further comprising: a data store storing the draft response, accessible by the first and second client devices.
 7. The computing system of claim 6 wherein the full content portion of the email message comprises a mail thread portion indicative of a full message thread corresponding to the email message, and an attachment, and wherein the full message generation logic is configured to detect actuation of the send actuator to send the draft response and to generate the full message including the unique portion of the draft response, the mail thread portion and the attachment.
 8. A computer implemented method, comprising: detecting, on an email server, that a user is generating, on a first client device, a draft response to an email message in a mailbox for the user, the email message including a full content portion; truncating the email message, to obtain a truncated email message that is less than the full content portion of the email message, on the email server; sending the truncated email message to the first client device for generation of the draft response; saving the draft response on the email server for access by the user from a second client device; detecting, on the email server, the user accessing the draft response from the second client device; and sending the truncated message and a unique portion of the draft response, entered in the draft response, to the second client device in response to detecting the user accessing the draft response from the second client device.
 9. The computer implemented method of claim 8 and further comprising: detecting, at the email server, actuation of a send actuator, on the second client device, to send the draft response; generating, at the email server, a full message including the unique portion of the draft response and the full content portion of the email message; and sending the full message to a recipient.
 10. The computer implemented method of claim 9 and further comprising: detecting a smart reply input from the first client device; and in response, generating the truncated message.
 11. The computer implemented method of claim 10 and further comprising: detecting the user accessing the draft response from the second client device; detecting a change in the full content portion of the draft response; and sending the full content portion of the draft response, along with the unique portion, to the second client device.
 12. The computer implemented method of claim 10 wherein saving the draft response on the email server comprises: saving the draft response on the email service as a draft in the mailbox for the user with a smart reply indicator indicating that the smart reply input, corresponding to the draft response, was detected.
 13. The computer implemented method of claim 12 and further comprising: storing the draft response in a cloud-based data store, accessible by the first and second client devices through the email server.
 14. The computer implemented method of claim 13 wherein the full content portion of the email message comprises a mail thread portion indicative of a full message thread corresponding to the email message, and an attachment, and wherein generating the full message comprises: detecting actuation of the send actuator to send the draft response; and generating the full message including the unique portion of the draft response, the mail thread portion and the attachment.
 15. A computing system, comprising: electronic mail (email) functionality on a hosted email service that determines that a user is generating, on a first client device, a draft response to an email message in a mailbox for the user, the email message including a full content portion; a smart reply system that truncates the email message, to obtain a truncated email message that is less than the full content portion of the email message, and sends the truncated email message to the first client device for generation of the draft response; a draft roaming system that saves the draft response on the hosted email service for access by the user from a second client device, the smart reply system sending the truncated message and a unique portion of the draft response, entered in the draft response, to the second client device in response to detection of the user accessing the draft response from the second client device; and full message generation logic configured to detect actuation of a send actuator to send the draft response and to generate a full message including the unique portion of the draft response and the full content portion of the email message, the email functionality sending the full message.
 16. The computing system of claim 15 wherein the smart reply system comprises: message truncation logic configured to generate the truncated message; and smart reply detection logic configured to detect a smart reply input from the first client device and, in response, control the message truncation logic to generate the truncated message.
 17. The computing system of claim 16 wherein the smart reply system comprises: draft change detector logic configured to detect a change in the full content portion of the draft response and control the draft roaming system to send the full content portion of the draft response, along with the unique portion, to the second client device in response to detection of the user accessing the draft response from the second client device.
 18. The computing system of claim 17 wherein the draft roaming system comprises: draft maintenance logic configured to save the draft response on hosted the email service as a draft in the mailbox for the user with a smart reply indicator indicating that the smart reply input, corresponding to the draft response, was detected by the smart reply detection logic.
 19. The computing system of claim 18 and further comprising: a cloud-based data store storing the draft response, accessible by the first and second client devices through the hosted email service.
 20. The computing system of claim 19 wherein the full content portion of the email message comprises a mail thread portion indicative of a full message thread corresponding to the email message, and an attachment, and wherein the full message generation logic is configured to detect actuation of the send actuator to send the draft response and to generate the full message including the unique portion of the draft response, the mail thread portion and the attachment. 